---
title: "sp82067_TimelinessOf1stPayment stored procedure documentation"
summary: "Retrieval record for the sp82067_TimelinessOf1stPayment procedure, not returned by the Legends CLI."
status: draft
owner: SAIF Documentation Generator
last_reviewed: "2026-08-31"
source_schema: "Unknown"
source_name: "sp82067_TimelinessOf1stPayment"
source_type: "PROCEDURE"
retrieval_status: "not-found-by-cli"
retrieval_command: "legends oracle query --name sp82067_TimelinessOf1stPayment"
retrieval_date: "2026-08-31"
---

# sp82067_TimelinessOf1stPayment

> [!WARNING]
> **Procedure source not returned by the database.** `sp82067_TimelinessOf1stPayment` was queried in Oracle via the Legends CLI on 2026-08-31 (`legends oracle query --name sp82067_TimelinessOf1stPayment`, attempted 2026-08-31T21:10:00Z) and no source was returned. This was a properly-executed retrieval attempt, not a skipped one. The referencing code is flagged as **possibly** dead code pending further investigation — this is not a definitive finding.

## Overview

| Field | Value |
| --- | --- |
| **Schema** | Unknown — not returned by CLI |
| **Type** | Unknown — presumed procedure from the BOF call site only (`CommandType.StoredProcedure`) |
| **Database** | Unknown — not returned by CLI |
| **Status** | ⚠️ Queried via Legends CLI on 2026-08-31; no source returned |
| **Query executed** | `legends oracle query --name sp82067_TimelinessOf1stPayment` |
| **Calling libraries** | `SAIF.Business.Claim` |
| **Calling classes** | `clsTimelinessOfFirstPayment` |

**Class-name / file-name discrepancy:** the source file is named `clsITimelinessOfFirstPayment.vb` (with an `I`), but the class it declares (line 37) is `clsTimelinessOfFirstPayment` (no `I`). The class name above is correct; the file path below retains the `I`, matching the file on disk.

## Possibly Dead Code References

The following .NET code path references this procedure. Because the database returned no source for it, this may be dead code — but this has **not** been confirmed. A not-found result is consistent with several unruled-out explanations: the object was dropped and the caller is genuinely orphaned; the object exists under a schema or synonym the CLI query did not resolve; the object exists but is not visible to the querying account's privileges; or the object lives in a different database instance or behind a database link.

| Class | Method | Source File |
| --- | --- | --- |
| `clsTimelinessOfFirstPayment` | `GetTimelinessOfFirstPayment` (entry point, line 321); `AddParm("inClaimID", …)` (line 212); `AddParm("requestType", "Detail", 6)` (line 214); `AddCursorParm("recordset", ParameterDirection.Output)` (line 216); `DataRequest.ID = "TimelinessPayment"` (line 217); `RetrieveSQL` returns the procedure name (line 438) | `SAIF.Business.Claim/clsITimelinessOfFirstPayment.vb` |

No parameter table, business rule, or operation can be produced for this procedure — its signature and body are unknown, and nothing beyond the caller-side `AddParm` names above may be asserted.

## Related Documentation
- [Procedure catalog](index.md)

## Sources
- Retrieved via `legends oracle query --name sp82067_TimelinessOf1stPayment` on 2026-08-31 — no source returned (not found by CLI)
- Referencing code: `SAIF.Business.Claim/clsITimelinessOfFirstPayment.vb` (lines 37, 212–217, 321, 438)